DRUID 5.14
Deployment Dates
The table below lists the deployment date of DRUID v5.14 across DRUID Clouds. To view the DRUID Releases Calendar, see Druid ChatBot Releases.
Druid Cloud Community *.community.Druidplatform.com |
Druid Cloud US *.us.Druidplatform.com |
Druid Cloud Australia *au.Druidplatform.com |
Druid Cloud West-Europe (PROD) *.Druidplatform.com |
---|---|---|---|
May 11, 2023 | June 08, 2023 | June 08, 2023 | June 08, 2023 |
These release notes give you a brief, high-level description of the improvements implemented to existing features.
If you have questions about your DRUID tenant, please contact support@Druidai.com or your local DRUID partner for more information.
- Native scripts support in the Connector fields of the response mapping
- REST Connector - For custom authentication, added support for tokens returned as string
- Custom Code - added support to set and get connector local variables.
What's New
- Knowledgebase - Unstructured Data sources (technology preview). You can now add unstructured data sources to the Knowledge base and crawl a website based on a specific crawling policy.
For more information, see Knowledge base.
Improvements
- Bot Summary Dashboard. The Engagement KPIs metric Users now take into account the number of unique authenticated users providing bot authors with a more relevant view on the bot usage.
- Max number of sessions for automatic allocation. When the maximum number of sessions for automatic allocation is set on a bot level and on the queue level, DRUID takes into consideration the minimum value between the bot level and queue level settings. If an agent is allocated to multiple queues with different maximum active sessions for automatic allocation set, DRUID takes into consideration the smallest value of them allocating clients to agents inth.
- NLU.NER.IndexBasedEntityExtractorV2. This is a new experimental NLP parameter set on the bot level that acts as a fallback additional algorithm when the default extraction algorithm fails to extract. Set this parameter to true to extract complex data from indexed entities, values comprised of multiple words. E.g. "Carol Davila University of Medicine and Pharmacy".
- CNN Document Builder - support for dynamic file name. You can now specify the file name of the generated document either hard coded as string (e.g., "Invoice April") or as a value from the context: an entity field (e.g., [[Employee]].Name) or a local variable.
- Native scripts support in the Connector fields of the response mapping. To use the response from APIs that send data into language specific JSON properties (a key from a response task might be in a native script; e.g., Latin script: "téléphone"). You can now map in the response keys that are in the following native scripts: Latin, Greek, Hebrew, Simplified Chinese, Traditional Chinese, Japanese, Hindi and Arabic.
- REST Connector - For custom authentication, added support for tokens returned as string. If the Authenticate client returns the token in the response body as a simple string instead of a JSON object (e.g., "345b4hjbdjk5j234544"), when mapping the token in the Authenticate Client Request response, specify text in the Connector field type column.
- Custom Code - added support to set and get connector local variables. You can now set and use connector local variables from the integration context between integration tasks.
-
LiveChat UI improvement for helpdesk agents. The conversation in which the agent is currently engaged with the client is marked with a gray bar displayed on the left and the other active live sessions are highlighted in orange.
- Origin validation is included in AuthoryzeAnonymousAsync. You can now prevent bots from being accessed from domains that are not yours by defining the Allowed Origins in the bot details page, section General. This adds an extra layer of security to your bot as the DRUID webchat will validate if the domain from where it is accessed corresponds to the Allowed Origins defined on the bot.
- Added security roles on solutions. DRUID administrators can now grant bot authors access to specific solutions by grating the Read Solution security role permission and selecting the security role(s) on the solution (Roles tab).
-
Read-only web forms. You can now prevent users from editing records by setting the desired web forms as read-only.
- Right side editor - full screen option. In the DRUID Portal you can now expand the right side editor to the entire diagram area.
For more information on the Engagement KPIs, see Bot Summary Dashboard.
Example: Queue A has the Max number of active sessions set to 2 and Queue B has the Max number of active sessions set to 3. The Max number of active sessions on the bot level is set to 4. If an agent is allocated to both Queue A and Queue B, the agent will be automatically allocated maximum 2 sessions in parallel for both queues; for Queue B the agent can manually take 2 more clients (to reach the maximum number of active sessions set on Queue B).
For more information, see Using Connector Local Variables.
Example:
Bug Fixes
- NER: Sample values modal were not saved in some cases.
- OAuth - Import Solution - App didn't have the integrations set.
- Flows were not linked after uploading solution train set.
- FE: Intent Not Recognized was not triggered or single match below the target score (hotfix applied on 5.11).
- Is Response Collection was not enabled on DRUID Data Service Query Templates.
- Expansion level was not set to 2 on DRUID Data Service Query Templates.
- Adaptive Cards were not inactivated after the inactivity cancel conversation message was displayed.
- The newly created workspaces were displayed only after refresh.
- Solution content entries were not visible only on "read" permission.